Release Notes PTV xServer 1.28
PTV xCluster Server
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
1.28.0.1
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xCluster and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xCluster won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xCluster won't start.
- Bugfix: The distance and driving period between two identical locations of a distance matrix is 0 in all cases.
PTV xDima Server
1.28.0.3
- Bugfix: The method 'deleteDima' reliably returns an error if persisted folders could not be removed from the hard drive.
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
1.28.0.1
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: Calculating a distance matrix with high-performance routing in combination with Road Editor data is possible.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xDima and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xDima won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xDima won't start.
- Bugfix: The distance and driving period between two identical locations of a distance matrix is 0 in all cases.
PTV xLoad Server
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
1.28.0.1
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xLoad and must be installed separately.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
PTV xLocate Server
1.28.0.2
- Improvement: Consider the extensive search mode only for multi-field search and not for single-field search.
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
1.28.0.1
- Improvement: Errors caused by using the SQL filter for geographic data stored in a database have clearer messages.
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xLocate and must be installed separately.
- Improvement: Switched on the extensive search mode in the default profile to get better results while accepting a moderate performance loss.
- Improvement: Updated the integrated HERE sample map.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
PTV xMap Server
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
1.28.0.1
- Improvement: Errors caused by using the SQL filter for geographic data stored in a database have clearer messages.
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xMap and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xMap won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: The Feature Layer 'PTV_TrafficIncidents' is visible again when using PTV Content Update Service in update on demand mode.
PTV xMapmatch Server
1.28.0.2
- Improvement: Database drivers are no longer shipped as they are not required.
1.28.0.1
- Improvement: Updated the stored profiles containing all relevant parameters explicitly instead of their default values.
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xMapmatch and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xMapmatch won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Bugfix: In case of a transition rating set to 0 there are no longer invalid loops calculated.
- Bugfix: The handling of possible loops in a tunnel is improved to avoid long calculation times.
PTV xRoute Server
1.28.0.2
- Improvement: The Road Editor database mode is available for 64-bit (set by property 'reDBConnection' in file 'xroute.properties').
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
- Bugfix: Fixed an internal cost calculation problem in combination with Feature Layer 'PTV_TrafficIncidents' and 'PTV_TruckAttributes' to assure that more routes are found.
1.28.0.1
- Improvement: Errors caused by using the SQL filter for geographic data stored in a database have clearer messages.
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xRoute and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xRoute won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xRoute won't start.
PTV xTerritory Server
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
1.28.0.1
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: Calculating a distance matrix with high-performance routing in combination with Feature Layer data is possible.
- Bugfix: Calculating a distance matrix with high-performance routing in combination with Road Editor data is possible.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xTerritory and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xTerritory won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xTerritory won't start.
- Bugfix: The distance and driving period between two identical locations of a distance matrix is 0 in all cases.
PTV xTour Server
1.28.0.2
- Improvement: Added a JDBC folder to deploy drivers for other databases than Apache Derby. That means that drivers for other databases are no longer shipped.
- Bugfix: Fixed the configuration of the job management at startup to assure the stability of the database connections.
- Bugfix: Better exception handling to prevent the optimization engine from being unusable in subsequent requests.
1.28.0.1
- Feature: Added support for multi-compartment constraints in the tour planning by using the new attribute 'enableMultiCompartmentConstraint'.
- Improvement: Some values on the server-side configuration file 'TourOpt.ini' are optimized. Please take this into account in case of modifying this file.
- Improvement: Updated Apache CXF to version 3.3.2 and revised the SOAP endpoint configuration to regain the former throughput of SOAP requests.
- Bugfix: Calculating a distance matrix with high-performance routing in combination with Road Editor data is possible.
- Bugfix: If PTV xServer runs behind a middleware/gateway and the X-Forwarded header fields are set, the service endpoints do contain proper URLs in the WSDL and WADL responses.
1.28.0.0
- Feature: Added new parameter 'mergeTransportPointCountPerSite' that counts all transport points at the same site as single transport point regarding the restriction 'maxTransportPointCountPerTour'.
- Feature: Added support for external Java installations (64-bit Java 8 required, Amazon Corretto or Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xTour and must be installed separately.
- Improvement: Updated the stored profiles to data compatibility version 2 as all current PTV maps are also based on data compatibility version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xTour won't start.
- Improvement: Updated the integrated HERE sample map suitable for the new stored profiles data compatibility version 2.
- Improvement: Updated Apache CXF to version 3.2.8.
- Improvement: Replaced BoneCP by HikariCP to improve the stability of database connections (e.g. when using POIs or jobs).
- Bugfix: In case of area tour planning in connection with trains and trailers, the right vehicle may have been missed.
- Bugfix: In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xTour won't start.
- Bugfix: The distance and driving period between two identical locations of a distance matrix is 0 in all cases.
PTV xServer bundle
1.28.0.3
- Includes: PTV xCluster Server 1.28.0.2
- Includes: PTV xDima Server 1.28.0.2
- Includes: PTV xLoad Server 1.28.0.2
- Includes: PTV xLocate Server 1.28.0.2
- Includes: PTV xMap Server 1.28.0.2
- Includes: PTV xMapmatch 1.28.0.2
- Includes: PTV xRoute Server 1.28.0.2
- Includes: PTV xTerritory Server 1.28.0.2
- Includes: PTV xTour Server 1.28.0.2
- Includes: PTV xServer add-on AJAX Maps 3.5.31.0
- Includes: Code Sample Browser 1.28.0.0
1.28.0.2
- Bugfix: Corrected the configuration in file 'wrapper.conf' to avoid conflicts of multiple backend instances at startup.
- Includes: PTV xCluster Server 1.28.0.1
- Includes: PTV xDima Server 1.28.0.1
- Includes: PTV xLoad Server 1.28.0.1
- Includes: PTV xLocate Server 1.28.0.1
- Includes: PTV xMap Server 1.28.0.1
- Includes: PTV xMapmatch 1.28.0.1
- Includes: PTV xRoute Server 1.28.0.1
- Includes: PTV xTerritory Server 1.28.0.1
- Includes: PTV xTour Server 1.28.0.1
- Includes: PTV xServer add-on AJAX Maps 3.5.31.0
- Includes: Code Sample Browser 1.28.0.0
1.28.0.1
- Includes: PTV xCluster Server 1.28.0.1
- Includes: PTV xDima Server 1.28.0.1
- Includes: PTV xLoad Server 1.28.0.1
- Includes: PTV xLocate Server 1.28.0.1
- Includes: PTV xMap Server 1.28.0.1
- Includes: PTV xMapmatch 1.28.0.1
- Includes: PTV xRoute Server 1.28.0.1
- Includes: PTV xTerritory Server 1.28.0.1
- Includes: PTV xTour Server 1.28.0.1
- Includes: PTV xServer add-on AJAX Maps 3.5.31.0
- Includes: Code Sample Browser 1.28.0.0
1.28.0.0
- Includes: PTV xCluster Server 1.28.0.0
- Includes: PTV xDima Server 1.28.0.0
- Includes: PTV xLoad Server 1.28.0.0
- Includes: PTV xLocate Server 1.28.0.0
- Includes: PTV xMap Server 1.28.0.0
- Includes: PTV xMapmatch 1.28.0.0
- Includes: PTV xRoute Server 1.28.0.0
- Includes: PTV xTerritory Server 1.28.0.0
- Includes: PTV xTour Server 1.28.0.0
- Includes: PTV xServer add-on AJAX Maps 3.5.31.0
- Includes: Code Sample Browser 1.28.0.0
Copyright © 2025 PTV Logistics GmbH All rights reserved. | Imprint